Cloud-based device twinning

ABSTRACT

A network-based service is utilized to facilitate twinning of two or more communication devices associated with a subscriber account. Incoming communication is intercepted by a communication device and forwarded to a network server, which in turn transmits the incoming communication to the multiple twinned devices. In addition, identifier data associated with outgoing communication is replaced with a primary identifier (e.g., customer telephone number (CTN)) of a user&#39;s primary device or a common identifier (e.g., a mobile one number (MON)) assigned to devices associated with the user&#39;s subscriber account. Communication devices can be temporarily twinned for a defined time period, during which a common bill can be generated for the twinned devices.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 16/101,364, filed on Aug. 10, 2018, andentitled “CLOUD-BASED DEVICE TWINNING”, which is a continuation of U.S.patent application Ser. No. 15/636,456 (now U.S. Pat. No. 10,057,738),filed on Jun. 28, 2017, and entitled “CLOUD-BASED DEVICE TWINNING”,which is a continuation of U.S. patent application Ser. No. 14/536,418(now U.S. Pat. No. 9,723,462), filed on Nov. 7, 2014, and entitled“CLOUD-BASED DEVICE TWINNING”. The entireties of the above notedapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The subject disclosure relates to wireless communications, e.g., tocloud-based device twinning.

BACKGROUND

As wearable devices begin to proliferate, it is common for consumers toown multiple mobile devices. For example, consumers can own a primarydevice, such as, a mobile phone and a secondary device, such as, a smartwatch, both having respective subscriber identity modules (SIMs) withassociated telephone numbers. Typically, it can get difficult toremember multiple telephone numbers associated with the different mobiledevices.

Further, conventionally, primary devices and wearable devicescommunicate via different peer-to-peer (P2P) networks, such as,Bluetooth® and/or near field communication (NFC). Using P2P protocols,notifications, calls, and/or messages received at a primary device canbe simply forwarded to the wearable device. Additionally, replies to theforwarded incoming calls/messages can be directly sent to the primarydevice from the wearable device via the P2P networks, for example, usinga keypad/touch screen and/or voice commands.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that provides cloud-based twinningof subscriber devices.

FIG. 2 illustrates an example system for configuration of twinneddevices.

FIG. 3 illustrates an example system that facilitates temporary twinningof a leased/rented device.

FIG. 4 illustrates an example record that is employed to initiatetwinning and/or un-twinning of user devices.

FIG. 5 illustrates an example system that facilitates routing ofcommunication data between twinned devices.

FIG. 6 illustrates an example system that facilitates billing fortwinned devices.

FIG. 7 illustrates an example system that facilitates automating one ormore features in accordance with the subject embodiments.

FIG. 8 illustrates an example method that facilitates routing ofincoming communication data for twinned devices.

FIG. 9 illustrates an example method that facilitates routing ofoutgoing communication data for twinned devices.

FIG. 10 illustrates an example method that facilitates configuration oftemporarily twinned devices.

FIG. 11 illustrates an example block diagram of a user equipmentsuitable for cloud-based device twinning.

FIG. 12 illustrates a Long Term Evolution (LTE) network architecturethat can employ the disclosed architecture.

FIG. 13 illustrates a block diagram of a computer operable to executethe disclosed communication architecture.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “node,” “server,” or the like are generally intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution or an entityrelated to an operational machine with one or more specificfunctionalities. For example, a component can be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, computer-executable instruction(s), aprogram, and/or a computer. By way of illustration, both an applicationrunning on a controller and the controller can be a component. One ormore components may reside within a process and/or thread of executionand a component may be localized on one computer and/or distributedbetween two or more computers. As another example, an interface caninclude input/output (I/O) components as well as associated processor,application, and/or API components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement one or moreaspects of the disclosed subject matter. An article of manufacture canencompass a computer program accessible from any computer-readabledevice or computer-readable storage/communications media. For example,computer readable storage media can include but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical disks (e.g., compact disk (CD), digital versatile disk(DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick,key drive . . . ). Of course, those skilled in the art will recognizemany modifications can be made to this configuration without departingfrom the scope or spirit of the various embodiments.

In addition, the word “example” or “exemplary” is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

Moreover, terms like “user equipment,” “communication device,” “mobiledevice,” “mobile station,” “mobile equipment,” “wearable device,”“primary device,” secondary device,” “subscriber device,” and similarterminology, refer to a wired or wireless device utilized by asubscriber or user of a wired or wireless communication service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Data and signaling streams can be packetized or frame-basedflows. Furthermore, the terms “user,” “subscriber,” “consumer,”“customer,” and the like are employed interchangeably throughout thesubject specification, unless context warrants particular distinction(s)among the terms. It should be appreciated that such terms can refer tohuman entities or automated components supported through artificialintelligence (e.g., a capacity to make inference based on complexmathematical formalisms), which can provide simulated vision, soundrecognition and so forth.

As an example, aspects or features of the disclosed subject matter canbe exploited in substantially any wired or wireless communicationtechnology; e.g., Universal Mobile Telecommunications System (UMTS),WiFi, Worldwide Interoperability for Microwave Access (WiMAX), GeneralPacket Radio Service (GPRS), Enhanced GPRS, Third Generation PartnershipProject (3GPP) Long Term Evolution (LTE), Third Generation PartnershipProject 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access(HSPA), ZigBee, or another IEEE 802.XX technology. Additionally,substantially all aspects of the disclosed subject matter can beexploited in legacy (e.g., wireline) telecommunication technologiesand/or future telecommunication technologies (e.g., 5G, whitespace,etc.).

Systems and methods disclosed herein relate to a cloud service thatenables twinning of multiple communication devices associated with asubscriber account. The term “twinning” as used herein refers toreplicating communications (e.g., transmission/reception of data) on twoor more communication devices. For example, when an incomingcommunication (call, message, and/or data) is directed to acommunication device, the notification for the incoming communicationwill be transmitted to the communication device as well as its twinnedcommunication device (simultaneously or substantially simultaneously),such that the incoming communication can be received via either of thecommunication devices. Further, systems and methods disclosed hereinenable users to utilize a primary identifier (e.g., telephone number) toshare voice and/or text messages and on multiple communication devices(with individual subscriber identity modules (SIMs)) associated withtheir subscriber account. As an example, the primary identifier can bean identifier (e.g., customer telephone number (CTN)) of a user'sprimary device or can be a common identifier (e.g., a mobile one number(MON)) assigned to multiple secondary devices associated with the user'ssubscriber account. In one aspect, incoming communication is interceptedby the primary device and forwarded to a cloud service, which in turntransmits the incoming communication to the multiple secondary devices.

Referring initially to FIG. 1, there illustrated is an example system100 that provides cloud-based twinning of subscriber devices, accordingto one or more aspects of the disclosed subject matter. System 100includes two or more user equipment (UEs) 102 ₁-102 _(N) (wherein N ismost any integer greater than 1) associated with (e.g., owned by, leasedby, rented by, used by, etc.) a common subscriber. As an example, theUEs 102 ₁-102 _(N) can include most any electronic communication devicessuch as, but not limited to, most any consumer electronic device, forexample, a tablet computer, a cellular phone, a personal computer, apersonal digital assistant (PDA), a smart phone, a laptop, a wearabledevice (e.g., smart watch, smart glasses, activity/fitness tracker,etc.), a digital media player, a digital camera, a content streamingplayer/dongle, a digital set-top box, a gaming system, etc. Further, theUEs 102 ₁-102 _(N) can also include, LTE-based devices, such as, but notlimited to, most any home or commercial appliance that includes an LTEradio and/or a connected vehicle (e.g., connected car, boat, plane,etc.). It can be noted that UEs 102 ₁-102 _(N) can be mobile, havelimited mobility and/or be stationary. In one example, UEs 102 ₁-102_(N) can include a multi-band, multi-mode, and/or multi-radio device.UEs 102 ₁-102 _(N) can be coupled to a communication network 104 (e.g.,cellular network, WiFi network, etc.) via one or more radio accessnetworks (RANs) (not shown).

System 100 utilizes a cloud/network to facilitate device twinning of UEs102 ₁-102 _(N). As an example, a cloud can include resources (e.g.,processing resource(s), data storage resource(s), etc.) that can resideon-premise or off-premise at a service provider location. Moreover, thecloud can be, but is not limited to, a public cloud, a private cloud, aninter-cloud, or a hybrid cloud. In one aspect, network server(s) 106 canbe part of the cloud. In one aspect, UEs 102 ₁-102 _(N) can includerespective subscriber identity modules (SIMs) 108 ₁-108 _(N) that areemployed to authenticate, register, and couple the UEs 102 ₁-102 _(N)with the communication network 104. Moreover, the SIMs 108 ₁-108 _(N)can store respective unique identifiers assigned to the UEs 102 ₁-102_(N), such as, but not limited to, customer telephone numbers (CTNs),Mobile Station International Subscriber Directory Numbers (MSISDNs),International mobile station equipment identity (IMEI), etc. As thenumber of devices associated with a common subscriber account increase,the number of identifiers (e.g., CTNs) that a user and/or hisfriends/family need to remember/recognize increases. System 100, vianetwork server(s) 106, allows the user and/or his friends/family toremember/recognize a single primary identifier (e.g., primary telephonenumber) and facilitates routing of a call or message to multiplecommunication devices associated with the user's subscriber account.Accordingly, system 100 enables utilization of one telephone number forall (or a selected set) of a user's devices. Moreover, when UEs 102₁-102 _(N) are twinned and communication data (e.g., voice/video calls,text messages, application data, etc.) directed to a first uniqueidentifier associated with a first UE (e.g., UE 102 ₁) is received, thecommunication data can be directed to the remaining UEs (e.g., UEs 102₂-102 _(N)) via the network server(s) 106.

According to an embodiment, UEs 102 ₁-102 _(N) can include respectivetwinning components 110 ₁-110 _(N) that can be utilized to intercept thecommunication data received by the UEs 102 ₁-102 _(N) and/or that is tobe transmitted from the UEs 102 ₁-102 _(N) and forward the communicationdata to the network server(s) 106 via the communication network 104. Inone aspect, the network server(s) 106 can include an In-App messagingapplication programming interface (API) and/or a cloud voice API thatfacilitates the routing of text messages and/or voice calls,respectively. As an example, for incoming communication data, thenetwork server(s) 106 can transmit the communication data to all thetwinned devices (e.g., UEs 102 ₁-102 _(N)), such that the communicationdata can be accessed by the user via any one (or more) of the devices(e.g., UEs 102 ₁-102 _(N)). As another example, for outgoingcommunication data, the network server(s) 106 can transmit thecommunication data to the destination device using a primary identifierselected from the respective unique identifiers assigned to the twinnedUEs 102 ₁-102 _(N). In one aspect, the twinning components 110 ₁-110_(N) can include, but are not limited to, twinning applications that areinstalled on UEs 102 ₁-102 _(N), for example, during provisioning,during manufacturing, via over-the-air signaling, on demand, etc.

Referring now to FIG. 2, there illustrated is an example system 200 forconfiguration of twinned devices, in accordance with an aspect of thesubject disclosure. In one aspect, system 200 can enable users to manage(e.g., activate and/or deactivate) twinning of their devices. It isnoted that the network server(s) 106 can include functionality as morefully described herein, for example, as described above with regard tosystem 100.

In one aspect, the network server(s) 106 can include a configurationcomponent 202 that can be employed for management of twinned devicesassociated with a user account. Moreover, the configuration component202 can receive user input 204 that is indicative of associating ordisassociating two or more devices (e.g., UEs 102 ₁-102 _(N)) of theuser. As an example, the user input 204 can be received from one or moreof the devices (e.g., UEs 102 ₁-102 _(N)) via an application downloadedon and/or installed on the device, and/or via a website/web serveraccessed by the user (e.g., via an account management webpage). It isnoted that the user input can be received at most any time, such as butnot limited to, on demand, on purchase/lease/rent of a new device, at aspecified time, in response to detection of an event, periodically, onrequest, etc. Additionally or optionally, the configuration component202 can verify that the user or user device is authorized to configurethe twinned devices, for example, by employing most any authenticationtechniques (e.g., passwords, credentials, pins, biometric data, etc.)

According to an aspect, the user input 204 can specify identifier dataindicative of devices, for which that twinning is to be initiated ordiscontinued. For example, the identifier data can include telephonenumbers (e.g., CTNs) associated with the devices. Additionally oroptionally, the user input 204 can specify timing data indicative of atime period for which the devices are to be twinned (or twinning is tobe discontinued). As an example, if a user has rented a device for aspecified time period, the user can request that the device be twinnedwith his primary device only for the duration of the time period. Inanother example, if the user has loaned out his secondary device (thatis twinned to his primary device), the user can request that thesecondary device be disassociated from his primary device (e.g., therequest can be sent on initiating the loan and/or prior to loaning thesecondary device). Moreover, in this example scenario, the secondarydevice be disassociated the primary device for the duration of the loanperiod. The configuration component 202 can store this user input 204 indata store 206 as subscriber records 208. It is noted that the datastore 206 can include volatile memory(s) or nonvolatile memory(s), orcan include both volatile and nonvolatile memory(s). Examples ofsuitable types of volatile and non-volatile memory are described belowwith reference to FIG. 13. The memory (e.g., data stores, databases) ofthe subject systems and methods is intended to comprise, without beinglimited to, these and any other suitable types of memory. Althoughdepicted as residing completely within the network server(s) 106, it isnoted that the data store 206 can reside partially within the networkserver(s) 106 and/or be locally (or remotely) coupled to the networkserver(s) 106.

Further, the user input 204 can also specify policies and/or rules forinitiation or disconnection of twinning and accordingly, theconfiguration component 202 can populate the subscriber records 208and/or store the policies and/or rules in the data store 206 as userpreferences 210. For example, the policies/rules can be based ongeographical locations of UEs, current time or date/date, type ofcommunication (e.g., forward only voice calls but not text messages,etc.), source or destination devices from/to which communications arereceived/directed, message priority, message size, distance between thetwinned UEs, etc. Additionally or optionally, the user input 204 canalso specify a telephone number (e.g., CTN) that is to be employed whilerouting outgoing communications from the user's devices (e.g., UEs 102₁-102 _(N)). For example, the telephone number can be a number (e.g.,CTN) associated with the user's primary device or can be the telephonenumber of the device that initiated the communication. Furthermore, inone example, the user input 204 can be a predefined text code (e.g.,*12, *11, etc.) that can activate or deactivate twinning of all devicesassociated with a subscriber account. Moreover, the text code can besent as a text message (e.g., short message service (SMS) message,multimedia messaging service (MMS) message, instant message, email,etc.) from one of the user's devices (e.g., UEs 102 ₁-102 _(N)) to anumber associated with the cloud service/network server(s) 106.Additionally, the configuration component 202 can also receive operatorpreferences 212 from one or more network devices (not shown) of thecommunication network (e.g., communication network 104) that can bestored in the data store 206. The network server(s) 106 can analyze theinformation stored within the data store 206 to facilitate routing ofcommunication directed to/received from the user's devices (e.g., UEs102 ₁-102 _(N)).

Referring now to FIG. 3, there illustrated is an example system 300 thatfacilitates temporary twinning of a leased/rented device, according toan aspect of the subject disclosure. As an example, system 300 can beutilized for linking, to a subscriber account, mobile-connected emergingdevices, which are typically used by the user for a pre-determinedperiod of time (e.g., lease term, rental time period, loan duration,etc.). The mobile-connected emerging devices can include most any UE,such as, but is not limited to a connected vehicle, rentalskis/equipment, etc. Typically, the user may not own themobile-connected emerging device but can rent, lease, and/or borrow themobile-connected emerging device for a specified time period. System 300enables the user and/or device owner/provider to temporarily twin themobile-connected emerging device with the user's primary devices duringthe specific period. In an example, the twinning can facilitatedetermination of a common bill for the usage of the mobile-connectedemerging device and the primary devices. It is noted that the networkserver(s) 106, the configuration component 202, the data store 206, thesubscriber records 208, the user preferences 210, and the operatorpreferences 212 can include functionality as more fully describedherein, for example, as described above with regard to systems 100 and200.

In one aspect, the configuration component can receive lessor input 302that is indicative of associating or disassociating two or more devices(e.g., UEs 102 ₁-102 _(N)) from a lessor (and/or renter, owner, businessentity, etc.) of the leased communication device. Moreover, the lessorinput 302 can be received from one or more devices via an applicationdownloaded on and/or installed on the devices, or via a website/webserver accessed by the lessor (e.g., via an account management webpage).It is noted that the lessor input 302 can be received at most any time,such as but not limited to, on demand, on purchase/lease/rent of a newdevice, at a specified time, in response to detection of an event,periodically, on request, etc. In an example scenario wherein a userrents a connected car, the car rental company, with the user's consent,can notify the user's primary device carrier network with the user'sprimary account phone number. The notification can be directed throughthe carrier network to the configuration component 202, which in turncan instruct an authorization component 304 to verify the user's consentto twin the user's primary device with the connected car. Theauthorization component 304 can utilize various authorization techniquesto confirm the user's consent. For example, the authorization component304 can transmit a consent confirmation request to the lessee's UE 306,for example, the user's primary device (e.g., UEs 102 ₁-102 _(N)).Moreover, the consent confirmation request can be transmitted via one ormore text messages (e.g., SMS message, MMS message, instant message,email, etc.). If confirmation is not received (e.g., within a definedtime period) or is rejected, the configuration component 202 canreject/block the lessor input 302 and deny twinning of devices.Alternatively, if confirmation (e.g., acknowledgement) is received fromthe lessee's UE 306, the configuration component 202 can twin the leaseddevice with the user's primary device (and/or one or more secondarydevices associated with the user's account).

According to an aspect, the lessor input 302 can specify identifier dataindicative of devices, for which that twinning is to be initiated ordiscontinued. For example, the identifier data can include telephonenumbers (e.g., CTNs) associated with the rental device (connected car,skiing gear, etc.). Additionally or optionally, the lessor input 302 canspecify timing data indicative of a time period for which the devicesare to be twinned (or twinning is to be discontinued). As an example, ifa user has rented a device for a specified time period, the lessor canrequest that the device be twinned with the user's primary device onlyduring that time period. The configuration component 202 can store thislessor input 302 in data store 206 as subscriber records 208. Further,the lessor input 302 can also specify policies and/or rules forinitiation or disconnection of twinning and accordingly, theconfiguration component 202 can populate the subscriber records 208and/or store the policies and/or rules in the data store 206 as lessorpreferences 308. The network server(s) 106 can analyze the informationstored within the data store 206 to facilitate routing of communicationdirected to/received from the user's devices, including the leaseddevice.

At the end of the rental period or termination of the lease contract,configuration component 202 can receive a device un-twinning requestfrom the lessor, via the lessor input 302. The authorization component304 can verify the user's content to un-twin the user's primary deviceand the leased device. For example, the authorization component 304 cantransmit a consent confirmation request to the lessee's UE 306, forexample, the user's primary device (e.g., UEs 102 ₁-102 _(N)). Moreover,the consent confirmation request can be transmitted via one or more textmessages (e.g., a SMS message, a MMS message, an instant message, email,etc.). If confirmation is not received (e.g., within a defined timeperiod) or is rejected, the configuration component 202 can reject/blockthe lessor input 302 and deny un-twinning of devices. Alternatively, ifconfirmation (e.g., acknowledgement) is received from the lessee's UE306, the configuration component 202 can un-twin the leased device fromthe user's primary device (and/or one or more secondary devicesassociated with the user's account).

Referring now to FIG. 4, there illustrated is an example record 400 thatis employed to initiate twinning (or un-twinning) of user devices inaccordance with the subject embodiments. As an example, record 400 canbe generated by the configuration component 202 (e.g., based on the userinput 204 and/or the lessor input 302) and stored in data store 206(e.g., as a subscriber record 208). Although information regarding onlytwo UEs (e.g., a primary UE and a secondary UE) are depicted in therecord 400, it is noted that the subject specification is not limited totwo UEs and multiple UEs can be associated with a subscriber account. Inthis example scenario, the primary UE is assigned a CTN#1 and thesecondary UE is assigned a CTN#2. Record 400 depicts the rulesassociated with routing communication data to/from the primary UE and/orsecondary UE.

As an example, when both the primary and secondary UEs are switched on,and twinning has been activated (e.g., twinning state is ON), incomingcommunication directed to either CTN (e.g., CTN#1 or CTN#2) isintercepted by the UE and forwarded (e.g., by the network server 106)simultaneously (or substantially simultaneously) to both the primary andsecondary UEs. Further, CTN#1 that is assigned to the primary UE can beutilized for outgoing communication received from the secondary UE.Alternatively, when both the primary and secondary UEs are switched on,and twinning has been deactivated (e.g., twinning state is OFF),incoming communication directed to CTN#1 is routed (e.g., by the networkserver 106) only to the primary UE, while incoming communicationdirected to CTN#2 is routed (e.g., by the network server 106) only tothe secondary UE. Since the UEs are un-twinned, outgoing communicationreceived from the secondary UE is forwarded (e.g., by the network server106) to the destination device with the CTN#2 that is assigned to thesecondary device.

In another example, when the primary UE is switched off, the secondaryUE is switched on, and twinning has been activated (e.g., twinning stateis ON), incoming communication directed to either CTN (e.g., CTN#1 orCTN#2) is intercepted and forwarded (e.g., by the network server 106) tothe secondary UE. Further, CTN#1 that is assigned to the primary UE canbe utilized for outgoing communication received from the secondary UE.Alternatively, when the primary UE is switched off, the secondary UE isswitched on, and twinning has been deactivated (e.g., twinning state isOFF), incoming communication directed to CTN#1 is routed (e.g., by thenetwork server 106) to the primary UE's voicemail, while incomingcommunication directed to CTN#2 is routed (e.g., by the network server106) only to the secondary UE. Since the devices are un-twinned,outgoing communication received from the secondary UE is forwarded(e.g., by the network server 106) to the destination device with theCTN#2 that is assigned to the secondary device.

In yet another example, when the primary UE is switched on, thesecondary UE is switched off, and twinning has been activated (e.g.,twinning state is ON), incoming communication directed to either CTN(e.g., CTN#1 or CTN#2) is intercepted and forwarded (e.g., by thenetwork server 106) to the primary UE. Alternatively, when the primaryUE is switched on, the secondary UE is switched off, and twinning hasbeen deactivated (e.g., twinning state is OFF), incoming communicationdirected to CTN#1 is routed (e.g., by the network server 106) only tothe primary UE, while incoming communication directed to CTN#2 is routed(e.g., by the network server 106) to the secondary UE's voicemail.

FIG. 5 illustrates an example system 500 that facilitates routing ofcommunication data between twinned devices, according to an aspect ofthe subject disclosure. As an example, system 500 can enable utilizationof a common number (e.g., CTN) to route communications to/from multipledevices associated with the user's subscriber account. It is noted thatthe UEs 102 ₁-102 ₂, the communication network 104, the networkserver(s) 106, the twinning components 110 ₁-110 ₂, the configurationcomponent 202, and the data store 206 can include functionality as morefully described herein, for example, as described above with regard tosystems 100-300.

In this example scenario, UE 102 ₁ can be considered as the user'sprimary device (e.g., cell phone) having a first CTN#1 and UE 102 ₂ canbe considered as the user's secondary device (e.g., wearable device,connected car, tablet computer, etc.) having a disparate second CTN#2.When the UEs 102 ₁-102 ₂ are twinned (e.g., by employing theconfiguration component 202), communication data (e.g. voice/videocalls, text messages, application data, etc.) transmitted by a sourcedevice 502 (e.g., another UE, content server, web server, etc.) anddirected to one of the CTNs (e.g., CTN#1 or CTN#2) can be rerouted toboth the UEs 102 ₁-102 ₂. Alternatively, when the UEs 102 ₁-102 ₂ areun-twinned (e.g., by employing the configuration component 202), thecommunication data transmitted from the source device 502 and directedto CTN#1, is routed to and presented via the UE 102 ₁, while thecommunication data transmitted from the source device 502 and directedto CTN#2, is routed to and presented via the UE 102 ₂.

As an example, if the source device 502 initiates a call to UE 102 ₁ byemploying CTN#1, the call data is directed to the UE 102 ₁ via thecommunication network 104 and is intercepted by the twinning component110 ₁. Prior to (or at most any time) the call notification beingprovided to the user via UE 102 ₁, the twinning component 110 ₁transmits the call data to the network server(s) 106. In one aspect, adata reception component 504 receives the call data and analyses thecall data along with data stored in the data store 206 (e.g., subscriberrecords, user preferences, operator preferences, lessor preferences,etc.). Based on the analysis, a data transfer component 506 can transmitthe call data to the appropriate devices. If determined by during theanalysis that the UEs 102 ₁-102 ₂ are twinned (and/or other preferencecriterion is satisfied), the call data can be routed simultaneously (orsubstantially simultaneously) to both UEs 102 ₁-102 ₂ and accordinglythe call notification (e.g., ring) can be presented via the UEs 102₁-102 ₂ simultaneously (or substantially simultaneously). If the userdecides to answer the call on UE 102 ₁, the call is dropped on UE 102 ₂,or if the user decides to answer the call on UE 102 ₂, the call isdropped on UE 102 ₁. However, if determined during the analysis that theUEs 102 ₁-102 ₂ are not twinned (and/or other preference criterion isnot satisfied), the call data can be routed only to UE 102 ₁. A similarprocedure is performed when the source device 502 initiates a call to UE102 ₂ by employing CTN#2, wherein the twinning component 1102 interceptsthe received call before the call notification is presented on UE 102 ₂and transmits the call data to the data reception component 504. Thedata reception component 504 analyses the call data along with datastored in the data store 206 and the data transfer component 506transmit the call data to the appropriate devices (e.g., UEs 102 ₁-102₂).

According to an embodiment, during outgoing communications (e.g.voice/video calls, text messages, application data, etc.) from thesecondary UE 102 ₂, to a destination device (e.g., another UE, contentserver, web server, etc.), the twinning component 110 ₂ intercepts theoutgoing communications and redirects the communication data to thenetwork server(s) 106. The data reception component 504 receives thecommunication data and analyzes the received data along with data storedin the data store 206 (e.g., subscriber records, user preferences,operator preferences, lessor preferences, etc.) Based on the analysis,the data transfer component 506 can mask and/or modify the identifier(e.g., CTN) of UE 102 ₂ and transmit the communication data to thedestination device 508 via the communication network 104. For example,if determined by during the analysis that the UEs 102 ₁-102 ₂ aretwinned, the CTN#2 of UE 102 ₂ can be replaced with CTN#1 of UE 102 ₁(or a MON assigned to the subscriber account) and the data transfercomponent 506 can transmit the communication data with the modified CTNto the destination device 508. However, if determined by during theanalysis that the UEs 102 ₁-102 ₂ are not twinned, the data transfercomponent 506 can transmit the communication data with the original CTN,CTN#2, to the destination device 508. In another example embodiment, thetwinning component 1102 can reroute intercepted outgoing communicationsdirectly to the primary UE 102 ₁, for example, via the communicationnetwork and/or one or more peer-to-peer network links (e.g., Bluetooth®,WiFi direct, near field communication (NFC), etc.). Further, thetwinning component 110 ₁ of the UE 102 ₁ can replace the identifier(e.g., CTN#2) of UE 102 ₂ received in the communication data with theidentifier (e.g., CTN#1) of UE 102 ₁ and transmit the communication datato the destination device 508 via the communication network 104.Accordingly, a single CTN can be utilized for multiple twinned UEsassociated with a common subscriber account to simplify billing and/orcaller identification.

Referring now to FIG. 6, there illustrated is an example system 600 thatfacilitates billing for twinned devices, according to one or moreaspects of the disclosed subject matter. It can be noted that the UEs102 ₁-102 _(N), the communication network 104, and the network server(s)106 can include functionality as more fully described herein, forexample, as described above with regard to systems 100-500. In oneaspect, the billing component 602 can monitor communications transmittedvia the communication network 104. Based on the various factors, suchas, but not limited to, destination device identifier, source deviceidentifier, bandwidth, speed, amount of data transmitted, time of day,etc., the billing component 602 can apply operator-defined charges andgenerate a bill for network usage. Moreover, for twinned devices thatutilize the same identifier (e.g., primary CTN or MON), a common billfor network usage by the multiple twinned devices can be generated bythe billing component 602. Moreover, for temporarily utilized (e.g.,rented, leased, borrowed) devices, such as, but not limited to a smartwatch (e.g., UE 102 ₂) and/or a connected car (e.g., UE 102 _(N)), thedevices can be twinned to the user's primary UE 102 ₁ for a defined timeperiod and accordingly, network usage charges associated with thetemporarily utilized devices can be provided to the user in a commonbill.

FIG. 7 illustrates an example system 700 that employs one or moreartificial intelligence (AI) components (702), which facilitateautomating one or more features in accordance with the subjectembodiments. It can be appreciated that the configuration component 202,the data store 206, the authorization component 304, the data receptioncomponent 504, and the data transfer component 506 can includerespective functionality, as more fully described herein, for example,with regard to systems 100-600. In an example embodiment, system 700(e.g., in connection with automatically twinning multiple devices) canemploy various AI-based schemes for carrying out various aspectsthereof. For example, a process for determining an when to twin two ormore devices, when to un-twin the two or more devices, an identifier(e.g., CTN and/or MON) that is to be utilized during outgoingcommunication from the twinned devices, routing of communication data tothe twinned devices, etc. can be facilitated via an automatic classifiersystem implemented by AI component 702.

A classifier can be a function that maps an input attribute vector,x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to aclass, that is, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. In the case of communicationsystems, for example, attributes can be information received from UEs,and the classes can be categories or areas of interest (e.g., levels ofpriorities). A support vector machine (SVM) is an example of aclassifier that can be employed. The SVM operates by finding ahypersurface in the space of possible inputs, which the hypersurfaceattempts to split the triggering criteria from the non-triggeringevents. Intuitively, this makes the classification correct for testingdata that is near, but not identical to training data. Other directedand undirected model classification approaches include, e.g., naïveBayes, Bayesian networks, decision trees, neural networks, fuzzy logicmodels, and probabilistic classification models providing differentpatterns of independence can be employed. Classification as used hereincan also be inclusive of statistical regression that is utilized todevelop models of priority.

As will be readily appreciated from the subject specification, anexample embodiment can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing access point/UE behavior, user/operator preferences orpolicies, historical information, receiving extrinsic data, mobilityperformance data, etc.). For example, SVMs can be configured via alearning or training phase within a classifier constructor and featureselection module. Thus, the classifier(s) of AI component 702 can beused to automatically learn and perform a number of functions, includingbut not limited to determining according to a predetermined criteriawhen two or more devices are to be twinned/un-twinned, a time periodduring which the two or more devices are twinned, a common identifier(e.g., CTN and/or MON) that is to be utilized during outgoingcommunication from the twinned devices, routing of communication data tothe twinned devices, etc. The criteria can include, but is not limitedto, historical patterns and/or trends, user preferences, serviceprovider preferences and/or policies, location of the twinned devices,current time/day, network load/traffic, billing preferences, and thelike.

FIGS. 8-10 illustrate a flow diagram and/or method in accordance withthe disclosed subject matter. For simplicity of explanation, the flowdiagrams and/or methods are depicted and described as a series of acts.It is to be understood and appreciated that the various embodiments arenot limited by the acts illustrated and/or by the order of acts, forexample acts can occur in various orders and/or concurrently, and withother acts not presented and described herein. Furthermore, not allillustrated acts may be required to implement the flow diagrams and/ormethods in accordance with the disclosed subject matter. In addition,those skilled in the art will understand and appreciate that the methodscould alternatively be represented as a series of interrelated statesvia a state diagram or events. Additionally, it should be furtherappreciated that the methods disclosed hereinafter and throughout thisspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methods to computers.The term article of manufacture, as used herein, is intended toencompass a computer program accessible from any computer-readabledevice or computer-readable storage/communications media.

Referring now to FIG. 8, illustrated is an example method 800 thatfacilitates routing of incoming communication data for twinned devices,according to an aspect of the subject disclosure. As an example, method800 can be implemented by one or more network devices of a communicationnetwork (e.g., a cellular network). The twinned devices can haveindependent identifiers, for example, CTNs, that can be utilized by asource device to direct communication (e.g., voice/video calls, textmessages, application data, etc.) to one of the twinned devices. Whenincoming communication is received at a first UE, a twinning applicationinstalled on the first UE can intercept the communication data andtransfer the communication data to a network device (e.g., prior topresenting the communication data and/or notification of thecommunication data). At 802, the incoming communication data, directedto the first UE, can be received from the first UE. At 804, it can bedetermined that the first UE is twinned with a second UE. As an example,the twinning data can be configured by the user of the UEs (and/orlessor/renter/owner of the second UE). The twinning data can be storedin subscriber records within a network data store along with userpreferences, operator preferences etc. In one example, the data storedwithin the network data store can be analyzed to determine routingpreferences for the incoming communication data. At 806, based on ananalysis of the data stored within the network data store, thecommunication data can be transmitted to both the first and the secondUEs. Moreover, a notification for the incoming communication data can bepresented on the first and the second UEs simultaneously (orsubstantially simultaneously).

FIG. 9 illustrates an example method 900 that facilitates routing ofoutgoing communication data for twinned devices, according to an aspectof the subject disclosure. As an example, method 900 can be implementedby one or more network devices of a communication network (e.g.,cellular network). The twinned UEs can have independent identifiers, forexample, CTNs, that can be utilized by a destination device for calleridentification. When an outgoing communication is initiated by a firstUE (e.g., in response to instructions received via an input interface ofthe first UE), a twinning application of the first UE intercepts theoutgoing communication and redirects the communication data to a networkdevice. At 902, the outgoing communication data, directed to thedestination device, is receive from the first UE. At 904, it can bedetermined that the first UE is twinned with a second UE. As an example,the twinning data can be configured by the user of the UEs (and/orlessor/renter/owner of the second UE). The twinning data can be storedin subscriber records within a network data store along with userpreferences, operator preferences etc. In one example, the data storedwithin the network data store can be analyzed to determine routingpreferences for the incoming communication data. At 906, based on ananalysis of the twinning data (and/or preferences), the first identifier(e.g., CTN) of the first UE in the communication data can be replacedwith a second identifier (e.g., CTN) of the second UE. In anotherexample, the first identifier (e.g., CTN) of the first UE can bereplaced with a MON assigned to the subscriber account. At 908, thecommunication data, with the replaced identifier, can be transmitted tothe destination device.

FIG. 10 illustrates an example method 1000 that facilitatesconfiguration of temporarily twinned devices, according to an aspect ofthe subject disclosure. As an example, method 1000 can be implemented byone or more network devices of a communication network (e.g., cellularnetwork). At 1002, request data to temporarily twin a UE with one ormore communication devices associated with a subscriber account can bereceived. As an example, the UE can comprise most any communicationdevice including, but not limited to connected vehicles, rentalequipment, etc. Further, the UE can be rented, leased, and/or borrowedfor a defined time period that can be included within the request data.At 1004, subscriber's consent to twin the UE with the one or morecommunication devices can be confirmed. For example, a text message(e.g., SMS message, MMS message, instant chat message, email, etc.) canbe sent to the subscriber's device to confirm consent. Moreover, onreceiving an acknowledgment in response to the text message, subscriberconsent can be confirmed. In another example, a customer servicerepresentative can call (e.g., voice call) the subscriber to receiveverbal confirmation. At 1006, instructions to facilitate twinning can bestored in a network data store, for example, within a subscriber record.Moreover, the instructions can be utilized to facilitate routing ofincoming and/or outgoing communications to/from the UE and/or the one ormore communication devices. In addition, the instructions can beutilized to facilitate masking of a device identifier for outgoingcommunications initiated by the UE. For example, the device identifier(e.g., CTN) of the UE can be replaced with a device identifier (e.g.,CTN) of one of the one or more communication devices and/or a MONassigned to the subscriber account.

To provide further context for various aspects of the subjectspecification, FIGS. 11 and 12 illustrate, respectively, a block diagramof an example user equipment 1100 that facilitates cloud-based devicetwinning and a wireless communication environment 1200, with associatedcomponents for operation and/or management of cloud-based devicetwinning in accordance with aspects described herein.

Referring now to FIG. 11, there is illustrated a block diagram of a UE1100 that facilitates cloud-based device twinning in accordance with thesubject specification. Moreover, the UE 1100 can be substantiallysimilar to and include functionality associated with UE 102 ₁-102 _(N),lessee UE 306, source device 502, and/or destination device 508,described herein. In one aspect, the UE 1100 can include a processor1102 for controlling all onboard operations and processes. A memory 1104can interface to the processor 1102 for storage of data and one or moreapplications 1106 being executed by the processor 1102. A communicationscomponent 1108 can interface to the processor 1102 to facilitatewired/wireless communication with external systems (e.g., viacommunication network 104). The communications component 1108 caninterface to a location component 1118 (e.g., GPS transceiver) that canfacilitate location detection of the UE 1100.

The UE 1100 can include a display 1110 (e.g., screen and/or touchscreen) for displaying received content (and/or content to betransferred) and/or for displaying text information related to operatingand using the device features. A serial I/O interface 1112 is providedin communication with the processor 1102 to facilitate serialcommunication (e.g., USB, and/or IEEE 1394) via a hardwire connection.Audio capabilities are provided with an audio I/O component 1114, whichcan include a speaker for the output of audio signals related to, forexample, recorded data or telephony voice data, and a microphone forinputting voice signals for recording and/or telephone conversations.

Further, the UE 1100 can include a slot interface 1116 for accommodatinga subscriber identity module (SIM) 108. Moreover, the SIM 108 can besubstantially similar to and include functionality associated with SIMs108 ₁-108 _(N). A unique CTN is associated with the SIM 108 that can beutilized as a device identifier for UE 1100. Firmware 1120 is alsoprovided to store and provide to the processor 1102 startup andoperational data. The UE 1100 can also include an image capturecomponent 1122 such as a camera and/or a video decoder 1124 for decodingencoded multimedia content. Further, the UE 1100 can include a powersource 1126 in the form of batteries, which power source 1126 interfacesto an external power system or charging equipment via a power I/Ocomponent 1128. In addition, the UE 1100 can include the twinningcomponent 110, which can be stored in memory 1104 and/or implemented byan application 1106. The twinning component 110 is substantially similarto twinning components 1101-110 _(N), can include respectivefunctionality, as more fully described herein, for example, with regardto systems 100 and 500.

FIG. 12 illustrates a high-level block diagram that depicts an exampleLTE network architecture 1200 that can employ the disclosedcommunication architecture. The evolved RAN for LTE consists of aneNodeB (eNB) 1202 that can facilitate connection of MS 1204 to anevolved packet core (EPC) network. In one aspect, the MS 1204 isphysical equipment or Mobile Equipment (ME), such as a mobile phone or alaptop computer that is used by mobile subscribers, with a Subscriberidentity Module (SIM). The SIM is associated with a CTN, anInternational Mobile Subscriber Identity (IMSI), IMEI, and/or MSISDN,which is a unique identifier of a subscriber. The MS 1204 includes anembedded client that receives and processes messages received by the MS1204. As an example, the embedded client can be implemented in JAVA. Itis noted that MS 1204 can be substantially similar to UEs 102 ₁-101 _(N)and/or 308, and can include functionality described with respect to 104_(A)-104 _(D), lessee UE 306, source device 502, destination device 508,and/or UE 1100 in systems 100, 300, 500, 600, and 1100.

The connection of the MS 1204 to the evolved packet core (EPC) networkis subsequent to an authentication, for example, a SIM-basedauthentication between the MS 1204 and the evolved packet core (EPC)network. In one aspect, the MME 1206 provides authentication of the MS1204 by interacting with the HSS 1208. The HSS 1208 contains asubscriber profile and keeps track of which core network node iscurrently handling the subscriber. It also supports subscriberauthentication and authorization functions (AAA). In networks with morethan one HSS 1208, a subscriber location function provides informationon the HSS 1208 that contains the profile of a given subscriber.

As an example, the eNB 1202 can host a PHYsical (PHY), Medium AccessControl (MAC), Radio Link Control (RLC), and Packet Data ControlProtocol (PDCP) layers that include the functionality of user-planeheader-compression and encryption. In addition, the eNB 1202 canimplement at least in part Radio Resource Control (RRC) functionality(e.g., radio resource management, admission control, scheduling, cellinformation broadcast, etc.). The eNB 1202 can be coupled to a servinggateway (SGW) 1210 that facilitates routing of user data packets andserves as a local mobility anchor for data bearers when the MS 1204moves between eNBs. In addition, the SGW 1210 can act as an anchor formobility between LTE and other 3GPP technologies (GPRS, UMTS, etc.).When MS 1204 is in an idle state, the SGW 1210 terminates a downlink(DL) data path and triggers paging when DL data arrives for the MS 1204.Further, the SGW 1210 can perform various administrative functions inthe visited network such as collecting information for charging andlawful interception.

In one aspect, the SGW 1210 can be coupled to a Packet Data NetworkGateway (PDN GW) 1212 that provides connectivity between the MS 1204 andexternal packet data networks such as IP service(s)/network(s) 1214.Moreover, the PDN GW 1212 is a point of exit and entry of traffic forthe MS 1204. It is noted that the MS 1204 can have simultaneousconnectivity with more than one PDN GW (not shown) for accessingmultiple PDNs.

The PDN GW 1212 performs IP address allocation for the MS 1204, as wellas QoS enforcement and implements flow-based charging according to rulesfrom a Policy Control and Charging Rules Function (PCRF) 1216. The PCRF1216 can facilitate policy control decision-making and controlflow-based charging functionalities in a Policy Control EnforcementFunction (PCEF), which resides in the PDN GW 1212. The PCRF 1216 canstore data (e.g., QoS class identifier and/or bit rates) thatfacilitates QoS authorization of data flows within the PCEF. In oneaspect, the PDN GW 1212 can facilitate filtering of downlink user IPpackets into the different QoS-based bearers and perform policyenforcement, packet filtering for each user, charging support, lawfulinterception and packet screening. Further, the PDN GW acts as theanchor for mobility between 3GPP and non-3GPP technologies such as WiMAXand 3GPP2 (CDMA 1X and EvDO). Although a LTE network architecture 1200is described and illustrated herein, it is noted that most anycommunication network architecture can be utilized to implement thedisclosed embodiments.

Referring now to FIG. 13, there is illustrated a block diagram of acomputer 1302 operable to execute the disclosed communicationarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 13 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1300 in which the various aspects of thespecification can be implemented. While the specification has beendescribed above in the general context of computer-executableinstructions that can run on one or more computers, those skilled in theart will recognize that the specification also can be implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices. The illustratedaspects of the specification can also be practiced in distributedcomputing environments where certain tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules can be located inboth local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, radio frequency (RF), infrared and other wirelessmedia.

With reference again to FIG. 13, the example environment 1300 forimplementing various aspects of the specification includes a computer1302, the computer 1302 including a processing unit 1304, a systemmemory 1306 and a system bus 1308. As an example, the component(s),server(s), equipment, system(s), and/or device(s) (e.g., UEs 102 ₁-102_(N), network server(s) 106, SIMs 108 ₁-108 _(N), twinning component 110₁-110 _(N), configuration component 202, authorization component 304,lessee UE 306, source device 502, data reception component 504, datatransfer component 506, destination device 508, billing component 602,AI component 702, UE 1100, MS 1204, eNB 1202, MME 1206, SGW 1210, PDN GW1212, PCRF 1216, etc.) disclosed herein with respect to system 100-300,500-700, and 1100-1200 can each include at least a portion of thecomputer 1302. The system bus 1308 couples system components including,but not limited to, the system memory 1306 to the processing unit 1304.The processing unit 1304 can be any of various commercially availableprocessors. Dual microprocessors and other multi-processor architecturescan also be employed as the processing unit 1304.

The system bus 1308 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1306includes read-only memory (ROM) 1310 and random access memory (RAM)1312. A basic input/output system (BIOS) is stored in a non-volatilememory 1310 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1302, such as during startup. The RAM 1312 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1302 further includes an internal hard disk drive (HDD)1314, which internal hard disk drive 1314 can also be configured forexternal use in a suitable chassis (not shown), a magnetic floppy diskdrive (FDD) 1316, (e.g., to read from or write to a removable diskette1318) and an optical disk drive 1320, (e.g., reading a CD-ROM disk 1322or, to read from or write to other high capacity optical media such asthe DVD). The hard disk drive 1314, magnetic disk drive 1316 and opticaldisk drive 1320 can be connected to the system bus 1308 by a hard diskdrive interface 1324, a magnetic disk drive interface 1326 and anoptical drive interface 1328, respectively. The interface 1324 forexternal drive implementations includes at least one or both ofUniversal Serial Bus (USB) and IEEE 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of thesubject disclosure.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1302, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to a HDD, a removable magnetic diskette, and a removableoptical media such as a CD or DVD, it should be appreciated by thoseskilled in the art that other types of storage media which are readableby a computer, such as zip drives, magnetic cassettes, flash memorycards, cartridges, and the like, can also be used in the exampleoperating environment, and further, that any such storage media cancontain computer-executable instructions for performing the methods ofthe specification.

A number of program modules can be stored in the drives and RAM 1312,including an operating system 1330, one or more application programs1332, other program modules 1334 and program data 1336. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1312. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1302 throughone or more wired/wireless input devices, e.g., a keyboard 1338 and/or apointing device, such as a mouse 1340 or a touchscreen or touchpad (notillustrated). These and other input devices are often connected to theprocessing unit 1304 through an input device interface 1342 that iscoupled to the system bus 1308, but can be connected by otherinterfaces, such as a parallel port, an IEEE 1394 serial port, a gameport, a USB port, an infrared (IR) interface, etc. A monitor 1344 orother type of display device is also connected to the system bus 1308via an interface, such as a video adapter 1346.

The computer 1302 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1348. The remotecomputer(s) 1348 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1302, although, for purposes of brevity, only a memory/storage device1350 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1352 and/orlarger networks, e.g., a wide area network (WAN) 1354. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1302 isconnected to the local network 1352 through a wired and/or wirelesscommunication network interface or adapter 1356. The adapter 1356 canfacilitate wired or wireless communication to the LAN 1352, which canalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1356.

When used in a WAN networking environment, the computer 1302 can includea modem 1358, or is connected to a communications server on the WAN1354, or has other means for establishing communications over the WAN1354, such as by way of the Internet. The modem 1358, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1308 via the serial port interface 1342. In a networkedenvironment, program modules depicted relative to the computer 1302, orportions thereof, can be stored in the remote memory/storage device1350. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1302 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g.,desktop and/or portable computer, server, communications satellite, etc.This includes at least WiFi and Bluetooth® wireless technologies. Thus,the communication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

WiFi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. WiFi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. WiFi networks use radio technologies called IEEE 802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWiFi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet). WiFinetworks operate in the unlicensed 5 GHz radio band at an 54 Mbps(802.11a) data rate, and/or a 2.4 GHz radio band at an 11 Mbps(802.11b), an 54 Mbps (802.11g) data rate, or up to an 600 Mbps(802.11n) data rate for example, or with products that contain bothbands (dual band), so the networks can provide real-world performancesimilar to the basic 10 BaseT wired Ethernet networks used in manyoffices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory in a single machine or multiple machines. Additionally, aprocessor can refer to an integrated circuit, a state machine, anapplication specific integrated circuit (ASIC), a digital signalprocessor (DSP), a programmable gate array (PGA) including a fieldprogrammable gate array (FPGA), a programmable logic controller (PLC), acomplex programmable logic device (CPLD), a discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. Processors can exploitnano-scale architectures such as, but not limited to, molecular andquantum-dot based transistors, switches and gates, in order to optimizespace usage or enhance performance of user equipment. A processor mayalso be implemented as a combination of computing processing units. Oneor more processors can be utilized in supporting a virtualized computingenvironment. The virtualized computing environment may support one ormore virtual machines representing computers, servers, or othercomputing devices. In such virtualized virtual machines, components suchas processors and storage devices may be virtualized or logicallyrepresented. In an aspect, when a processor executes instructions toperform “operations”, this could include the processor performing theoperations directly and/or facilitating, directing, or cooperating withanother device or component to perform the operations

In the subject specification, terms such as “data store,” data storage,”“database,” “cache,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory” or componentscomprising the memory. It will be appreciated that the memorycomponents, or computer-readable storage media, described herein can beeither volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory. By way of illustration, and notlimitation, nonvolatile memory can include read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

What has been described above includes examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methods for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “includes” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingconfiguration data that links a first smart device to a second smartdevice, wherein the first smart device and the second smart device areassociated with a common subscriber account; and based on theconfiguration data, facilitating a routing of communication data to thesecond smart device and the first smart device, wherein thecommunication data has been transmitted from a source device and isdetermined to be directed to the first smart device.
 2. The system ofclaim 1, wherein the configuration data comprises association data thatlinks a first identifier of the first smart device with a secondidentifier of the second smart device.
 3. The system of claim 1, whereinthe operations further comprise: storing the configuration data within anetwork storage device of a communication network.
 4. The system ofclaim 1, wherein the receiving comprises receiving the configurationdata from a user device subsequent to verifying that the user device isauthorized to configure the first smart device and the second smartdevice.
 5. The system of claim 1, wherein the configuration datacomprises timing data that specifies a time period for which the firstsmart device is to be linked to the second smart device.
 6. The systemof claim 1, wherein the configuration data comprises policy data thatspecifies a policy that is to be utilized to link the first smart devicewith the second smart device.
 7. The system of claim 6, wherein thepolicy is based on distance data representing a distance between thefirst smart device and the second smart device.
 8. The system of claim6, wherein the policy is based on classification data indicative of atype of the source device.
 9. The system of claim 6, wherein the policyis based on timing data indicative of a current time.
 10. The system ofclaim 6, wherein the policy is to be implemented in response toreceiving a predefined text code from an authorized user device.
 11. Thesystem of claim 1, wherein the first smart device and the second smartdevice are different type of smart devices.
 12. The system of claim 1,wherein, subsequent to the routing, notification data indicative of anotification associated with the communication data is to be presentedvia the second smart device and the first smart device.
 13. A method,comprising: receiving, by a system comprising a processor, configurationdata that links a first smart device and a second smart device, with acommon subscriber account; and based on the configuration data,facilitating, by the system, a presentation of notification dataindicative of a notification associated with communication data via thefirst smart device and via the second smart device, wherein thecommunication data is determined to be directed from a source device tothe first smart device.
 14. The method of claim 13, wherein thereceiving the configuration data comprises receiving policy data thatspecifies a policy for linking the first smart device and the secondsmart device with the common subscriber account.
 15. The method of claim13, further comprising: receiving, by the system, authorization datathat authorizes an association of the first smart device and the secondsmart device, with the common subscriber account.
 16. The method ofclaim 13, further comprising: as a function of the presentation,receiving, by the system, input data via the second smart device; and inresponse to receiving the input data, facilitating, by the system, arouting of the communication data to the second smart device.
 17. Themethod of claim 13, further comprising: storing, by the system, theconfiguration data within a data store of a communication network.
 18. Anon-transitory machine-readable storage medium, comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising: determining configuration data that links afirst smart device and a second smart device, with a common subscriberaccount; and in response to receiving communication data that isdirected from a source device to the first smart device, facilitating,based on the configuration data, a display of notification dataindicative of a notification associated with communication data via thefirst smart device and via the second smart device.
 19. Thenon-transitory machine-readable storage medium of claim 18, wherein thefirst smart device comprises a wearable device.
 20. The non-transitorymachine-readable storage medium of claim 18, wherein the first smartdevice comprises a device of a connected car.